Motivation:

#1152

Description:

The email action is implemented so that it validates all relevant values provided in the configuration file, inside the constructor. When performing the action, the email body is read from a template file, the path for which is provided in the configuration. We then fill in the values in the template with the respective job-specific information.

Please note that this is a first and basic implementation of the email action, which acts as a proof of concept for the Jobs MVP. The mailer (i.e. SMTP) is not property set up, so in the end we never actually send the email. Instead, we only perform validation and templating, and print the result of what the email content would look like, in the console.

Changes:

• In jobConfig.example.json: included configuration for the email action. It is possible that this is not the final schema, especially when it comes to providing the value for password. TBD as it is dependent on how the mailer service is set up in the facility. Please note the assumption that bodyTemplate should be the path to the template file.
• job-template-simplified.html is a minimal template example that requires only some basic job information. To be expanded.
• emailaction.ts: based on previous changes in the Action class, all validation is performed inside the constructor. Setting up mailService is commented out as we are currently not actually making the connection to the service. We open and read the file for which the path is provided in bodyTemplate. We fill in the template with the job details. Only the necessary fields are exposed to the template via jobTemplateOptions. In the end, instead of sending an actual email, we print the result in the console.
• jobs.controller.ts: applied a fix in order to always correctly provide to the template a list of datasetIds inside jobParams.